Rule Repository Service Interface |
|
The Rule Repository service is used to configure the settings for Rule execution.
Table 1. Fields on the Rule Repository Tab
| Field | Description | |
|---|---|---|
| Select Database Configuration | To create a Database Configuration | Select the New Database Configuration option from the drop-down list and provide the required information in the dialog box that appears. |
| To continue with an existing Database Configuration | Select it from the drop-down list. The associated fields are automatically filled. | |
| Advanced Options | Expand the group box and provide the necessary details. Note: Setting Cursor Cache Size to a high value would cause high memory consumption. Based on the application usage, adminstrator has to set an optimal value. This is also applicable to the Query Cache size. For example: The optimal cursor cache size can be between 50 - 100, subjective to the application usage. |
|
| Runtime Properties | Rule Action Threads | The number of threads required to execute the external actions, such as
If the number of transactions performed by the rule engine, involving external actions, is huge, increase the size of the rule action threads. The default size is 5 |
| Max. value for Dispatcher queue size | Maximum number of asynchronous rule actions that can be queued in the dispatcher queue. The default size is 50000. Note: Setting it to 0 will allow infinite number of rule actions in the queue and may result in Out of Memory error. Depending on the application's requirements, change the size of the dispatcher queue. Higher value of the parameter allows for higher memory and lower value limits memory usage. It is exposed to JMX as a cold setting. |
|
| Trace Rule Execution | Enables tracing of the rules.Select the check box to enable rule tracking. Note: Enabling this option will impact the performance as this feature demands the recording of details in database during the rule execution. |
|
| Monitor Request and Response | Enables the persistence of SOAP request and response of external actions | |
| Custom Rule Monitor Listener | Provide a fully qualified class name of the custom listener java class to access the rule execution data. This class should implement the Java interface com.cordys.bre.rim.RuleMonitor. The Rule Monitor implementation should return the class implementing com.cordys.bre.rim.RuleSessionListener. The RuleSessionListener interface contains the various set of events which needs to be implemented by the users. The events provides the API's to access Input / output message for a Rule, Rule set details, request and response details of rule actions etc. For more details, refer to Java documentation |